feat(mcp): add lexical capability ranking#2573
Closed
reachjalil wants to merge 3 commits into
Closed
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
Contributor
|
@reachjalil is attempting to deploy a commit to the Different AI Team on Vercel. A member of the Team first needs to authorize it. |
reachjalil
marked this pull request as ready for review
July 13, 2026 18:55
reachjalil
marked this pull request as draft
July 17, 2026 08:22
Collaborator
Author
|
Superseded by #2966, rebuilt on current dev with the valuable lexical relevance fixtures preserved and current capability contracts intact. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Warning
Queue audit (2026-07-17): returned to draft — do not merge this revision. The lexical-ranking idea is still potentially valuable, but the capability corpus and source contracts have changed since this branch. Rebuild it as a small current-
devranker/benchmark change with relevance fixtures and latency evidence instead of resolving the stale integration patch.Manager summary
This replaces source-specific additive keyword scoring with one dependency-free lexical ranker for the full Den capability corpus. REST, administrator, External MCP, marketplace, and skill candidates are merged and ranked on the same 0–100 response scale.
The public contract is unchanged:
/mcp/agentstill exposes onlysearch_capabilitiesandexecute_capability, and execution/authentication rules remain owned by each source.What changed
needs_connectionand error rows remain discoverable even when ordinary noisy matches are suppressed.Safety and runtime behavior
Evidence
invite a teammateandstore a notevocabulary gaps.Reviewer focus
needs_connectionrows.